add cua replay example script #1162
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Greptile Overview
Greptile Summary
Refactored the CUA replay example to demonstrate cache performance benefits by executing the same task twice - first to build the cache, then to replay from cache. The script now includes performance metrics showing duration comparison, time saved, and speedup percentage between cold and cached runs.
- Extracted logic into
runDemo()function that runs twice with different cache states - Added performance tracking with start/end timestamps
- Replaced drag-drop demo with login flow demo using modern login site
- Added formatted console output showing performance comparison table
- Imported
v3Loggeranddotenvfor logging and environment configuration
Issue Found:
- Typo in email address (
browserbaser.cominstead ofbrowserbase.com)
Confidence Score: 4/5
- Safe to merge after fixing the email typo - this is an example script demonstrating cache functionality
- Minor syntax error (typo) that needs correction but doesn't affect the core demonstration logic. The refactoring improves the example by clearly showing cache benefits with performance metrics.
- packages/core/examples/v3/cuaReplay.ts - fix email typo on line 36
Important Files Changed
File Analysis
| Filename | Score | Overview |
|---|---|---|
| packages/core/examples/v3/cuaReplay.ts | 4/5 | Refactored example to demonstrate CUA cache performance by running two passes and comparing execution times. Contains typo in email address that should be fixed. |
Sequence Diagram
sequenceDiagram
participant User
participant Main
participant RunDemo1 as runDemo(1)
participant V3_1 as V3 Instance 1
participant Agent1 as Agent (CUA)
participant Cache
participant RunDemo2 as runDemo(2)
participant V3_2 as V3 Instance 2
participant Agent2 as Agent (CUA)
User->>Main: Execute main()
Main->>RunDemo1: await runDemo(1)
RunDemo1->>V3_1: new V3({ cacheDir: "cua-agent-cache" })
RunDemo1->>V3_1: init()
V3_1->>RunDemo1: Browser context ready
RunDemo1->>Agent1: agent({ cua: true })
RunDemo1->>Agent1: execute(instruction)
Agent1->>Cache: Write actions (BUILDING CACHE)
Agent1->>RunDemo1: Result + duration
RunDemo1->>Main: metrics1 (cold run)
Main->>Main: Wait 2 seconds
Main->>RunDemo2: await runDemo(2)
RunDemo2->>V3_2: new V3({ cacheDir: "cua-agent-cache" })
RunDemo2->>V3_2: init()
V3_2->>RunDemo2: Browser context ready
RunDemo2->>Agent2: agent({ cua: true })
RunDemo2->>Agent2: execute(instruction)
Agent2->>Cache: Read cached actions (USING CACHE)
Cache->>Agent2: Replay actions (no LLM calls)
Agent2->>RunDemo2: Result + duration
RunDemo2->>Main: metrics2 (cached run)
Main->>User: Performance comparison table
1 file reviewed, 1 comment
seanmcguire12
approved these changes
Nov 5, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
why
Update example script to show benefits from using cached actions
image of what the final log looks like
what changed
test plan